Release 10.1A: OpenEdge Data Management:
Database Administration


PROMON Record Locking Table option

Displays the contents of the record locking table. Each line corresponds to an entry in the locking table. The lock table contains entries for all record locks currently granted or requested by users of the database. Figure 19–5 shows an example of this option’s output.

Record Locking Table: 
Usr Name     Chain #      Rec-id   Table Lock  Flags  Tran State      Tran ID 
  6 shannon  REC  120        102      18 EXCL         Begin            2619 
  7 shannon  REC  120        102      18 SHR          Begin            2620 
  8 shannon  REC  120        102      18 SHR          Dead             0    
RETURN - repeat, U - continue uninterrupted, Q - quit 

Figure 19–5: Sample output for PROMON Record Locking Table option

The size of the record locking table is set with the Locking Table Entries (-L) startup parameter. See the chapter on locks in OpenEdge Development: Progress 4GL Handbook for more information on locks and locking.

Usr

The user number.

Name

For client processes, the user name.

Chain

The chain type should always be REC, the record lock chain.

#

The record lock chain number. The locking table is divided into chains anchored in a hash table. These chains provide for fast lookup of record locks by Rec-id.

Rec-id

The record ID for the lock table entry. The Rec-id column identifies the records locked by each database process.

Table

The ID of the locked table.

Lock

One of five lock types: X (exclusive lock), S (share lock), IX (intent exclusive lock), IS (intent share lock), or SIX (shared lock on table with intent to set exclusive locks on records).

Flags

There are five possible types of flags: L, P, Q, or U. Table 19–3 lists the flags and their meanings.

Table 19–3: Flag values 
Flag
Name
Description
L
Limbo lock
The client has released the record, but the transaction has not completed. The record lock is not released until the transaction ends.
P
Purged lock entry
The lock is no longer held.
Q
Queued lock request
Represents a queued request for a lock already held by another process.
U
Upgrade request
The user has requested a lock upgrade from SHARE to EXCLUSIVE but is waiting for another process that holds a conflicting lock.
H
No hold
The “nohold” flag is set.

Trans State

The state of the transaction. Table 19–4 lists the possible states.

Table 19–4: Transaction states
State
Description
Begin
A transaction table entry was allocated, and a start record is being logged.
Active
The transaction is doing forward processing.
Dead
The transaction is complete, but the lock has not been released.
Prep
The transaction is preparing to enter phase 1 (ready to commit), but has not sent a ready-to-commit reply.
Phase 1
In phase 1, ready to commit.
Phase 2
In phase 2.
C
With two-phase commit, this user is logging for the coordinator for the transaction.
R
Ready to commit.
L
Limbo transaction.
Active JTA
The transaction is currently executing.
Idle JTA
The transaction is not currently executing.
Prepared JTA
The transaction is prepared.
RollbackOnly JTA
The transaction has encountered an error.
Committed JTA
The transaction is in the commit process.

Trans ID

Transaction ID of the lock.


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095